Macho Man Randy Savage
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Was up too late night. Just to add...as I can't edit the post (guess there is some time limit on edits) but the color space returned by CGColorSpaceCreateDeviceRGB() should be set to a variable and released with CGColorSpaceRelease instead of directly assigning the returned color space to rgbFormat.colorSpace like shown above.
I don't see how I can publish it with this feature being so broken on the latest version of iOS. I don't see how it helps me to release something that doesn't work.
Not sure how they are doing versioning..maybe using a lower "base sdk" would cause AVFoundation to use an older codepath that would avoid the issue but then I'd lose all iOS 17 symbols and would get my codebase in a huge mess. I have doubts that that would work anyway.
And on iOS version 17.0.3.
I meant to say "Include the view controller's view that you are presenting from in the array."
Seems on Sonoma using -performSelectorOnMainThread:withObject:waitUntilDone:modes: is not necessary. When testing on Ventura yesterday that was the only way I could get the menu to update.
Thanks a lot for your reply!
I seem to be getting better results listening for the window's onpageshow instead of the document.visibilitychange (and checking the visibility state of the document in the event handler to see if its visible) so I think I'm going to remove the document visibilitychange listener and replace it with pageshow.
_> I don't appear to have a memory leak here so I'm not sure why my address space limit would keep accumulating as I continue scrolling the table view. _
Looks like the returned UIImages (created with the CGImages) need to be released. They UIImages are stored in a NSCache. Unfortunately NSCache is not automatically removing objects when malloc_error_break is hit. The operating system isn't sending my app a memory warning either. I was under the impression NSCache would remove objects at the appropriate time based on certain OS conditions (like this one) automatically. I guess I should be able to resolve this by setting a count limit on the cache and/or manually emptying the cache when CGImageSourceCreateThumbnailAtIndex returns NULL. After manually emptying the cache of UIImages I'm able to load more without getting another cannot allocate memory error.